Suppress warnings in validation notebook (#587)#1696
Open
vahid-ahmadi wants to merge 1 commit into
Open
Conversation
The original 2022 report ("Aggregates in full") referred to a section that
has since been rewritten away, and the current saved outputs are already
clean. Add an explicit warnings filter at the top of the notebook so a
future kernel re-run (e.g. pandas FutureWarning from pd.concat in a loop)
doesn't leak warning streams back into the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/book/validation/validation.ipynbis a single hide-input cell that renders one Plotly figure and ships with clean saved outputs (no stream warnings)._config.ymlhasexecute_notebooks: off, so cleanliness today depends entirely on what's checked into the .ipynb. Add an explicitwarnings.filterwarnings(\"ignore\")at the top of the notebook so a future re-run (e.g. the FutureWarning frompd.concat([df, pd.DataFrame(...)])inside the loop) doesn't leak back into the docs.Test plan
docs/book/validation/validation.ipynb(the docs build job will exercise this).🤖 Generated with Claude Code